Add debug fields to DEA Intertidal to investigate x and y coordinates#1416
Merged
Add debug fields to DEA Intertidal to investigate x and y coordinates#1416
Conversation
robbibt
changed the title
erialC-P
approved these changes
Mar 26, 2026
Collaborator
erialC-P
left a comment
erialC-P
left a comment
There was a problem hiding this comment.
What a weird bug! Hopefully these temp debug fields will help get it sorted. Good luck
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adding some additional temporary debug fields to the DEA Intertidal feature info data to try and bugfix a confusing issue where radically different GridSpec tiles are returned for coordinates that are right next to each other.
E.g.
x094/y093here:https://ows.dev.dea.ga.gov.au/wms?exceptions=XML&version=1.3.0&feature_count=101&time=2023-01-01&styles=intertidal_elevation_adaptive&service=WMS&request=GetFeatureInfo&layers=ga_s2ls_intertidal_cyear_3&bbox=12999798.274516497%2C-4166735.285881527%2C13000409.770742778%2C-4166123.789655246&width=512&height=512&crs=EPSG%3A3857&query_layers=ga_s2ls_intertidal_cyear_3&info_format=application%2Fjson&i=310&j=19
vs.
x-213y-168here:https://ows.dev.dea.ga.gov.au/wms?exceptions=XML&version=1.3.0&feature_count=101&time=2023-01-01&styles=intertidal_elevation_adaptive&service=WMS&request=GetFeatureInfo&layers=ga_s2ls_intertidal_cyear_3&bbox=13000409.770742778%2C-4166735.285881527%2C13001021.266969059%2C-4166123.789655246&width=512&height=512&crs=EPSG%3A3857&query_layers=ga_s2ls_intertidal_cyear_3&info_format=application%2Fjson&i=151&j=121
This seems to occur on either side of the EPSG:3857 x=13000000 boundary, but I am still verifying this.